Skip to content

fix: update skips different file type#956

Merged
tridge merged 1 commit into
RsyncProject:masterfrom
steadytao:fix-update-replaces-different-file-type
Jun 4, 2026
Merged

fix: update skips different file type#956
tridge merged 1 commit into
RsyncProject:masterfrom
steadytao:fix-update-replaces-different-file-type

Conversation

@steadytao

Copy link
Copy Markdown
Member

Fixes #827 by making --update skip newer destination entries only when the destination file type matches the source file type.

The manpage says a file-format difference between sender and receiver is important enough for an update regardless of timestamps. However, a newer destination symlink could cause a source regular file to be skipped before the different-type replacement path was reached.

This keeps the existing newer-destination skip for matching file types but lets different file types continue to the replacement logic.

@tridge tridge left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks!

@tridge tridge force-pushed the fix-update-replaces-different-file-type branch from d0d85e5 to 769e6e0 Compare June 4, 2026 23:27
@tridge tridge merged commit cb44fc5 into RsyncProject:master Jun 4, 2026
13 checks passed
@steadytao steadytao deleted the fix-update-replaces-different-file-type branch June 6, 2026 02:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

--update incorrectly skips update when source is a file and destination is a symlink

2 participants